Strange baseline behavior

Hello,

 

I've stumbled upon some wacky baseline behavior that I didn't think was even possible in one of my modules.  The baselines are out of order (see attached screenshot).

 

They go 2.1 then 3.0 then 2.2, the most recent being 2.6

I have no idea how this happened (I was not here yet at the time these weird baselines were created).

I've done some testing with an archived & restored copy and it seems we are in for some trouble when they actually are ready to go to 3.0.  If we try to do a major baseline on the module alone, DOORS displays a message that it can't create 3.0 because 3.0 already exists.  If we try to do a major baseline of the module as a member of a baseline set, it overwrites the existing 3.0 with a new 3.0.   If I try using DXL with create (nextMajor, "" )  I get the "baseline already exists" error in the DXL window.

I've tried to recreate it every way I can think of, and I'm stumped.  Does anyone have any idea what might have happened with this?

 

Thanks!


emily.butt - Mon Jan 06 15:00:47 EST 2014

Re: Strange baseline behavior
Mathias Mamsch - Tue Jan 07 04:15:48 EST 2014

Hi Emily, I saw that kind of behaviour in the past, when the creation of a baseline failed with a crash of the DOORS client. In this case, the baseline was created, but the current baseline index was not updated. From your list it seems, that the problem occurred in 07/2013 but people kept creating baselines afterwards. So now when you try to create a baseline 3.0 the DOORS client complains.

I think you will not be able to do something on client side. A Database repository modification seems to be necessary - so you should ask the IBM support to fix the problem for your module.

Regards, Mathias